Repository navigation
Conversation
…CURITY.md, and update CodeRabbit path instructions.
…g redundant tasks and updating related configurations and documentation.
…l v1.3.0 GIF and glass theme features.
…sia, and React across applications and packages.
…nd remove old roadmap and architecture files.
📝 WalkthroughWalkthroughAdds v1.3.0 updates: rolling 12‑month contribution window in the GitHub client, renderer visual tapering and related test updates, CLI default frame-delay change, numerous docs/README additions and removals, Node/Bun and package version bumps, script/workflow reorganizations, and CI/tooling adjustments. Changes
Sequence Diagram(s)sequenceDiagram
participant Client as Caller (CLI/API)
participant Handler as fetchContributions()
participant Fetcher as fetchContributionsHTML()
participant YearFetch as fetchYear(year)
participant GitHub as GitHub HTML
participant Parser as parseContributionCalendar()
participant Merger as MergeRollingWindow
Client->>Handler: request(username, year)
Handler->>Fetcher: fetchContributionsHTML(username, year)
alt current year (rolling)
Fetcher->>YearFetch: fetchYear(currentYear)
Fetcher->>YearFetch: fetchYear(prevYear)
YearFetch->>GitHub: GET /users/:username/contributions?year=...
GitHub-->>YearFetch: HTML or 404
YearFetch-->>Fetcher: parsed days/weeks
else past year (calendar)
Fetcher->>YearFetch: fetchYear(targetYear)
YearFetch->>GitHub: GET /users/:username/contributions?year=targetYear
GitHub-->>YearFetch: HTML
YearFetch-->>Fetcher: parsed days/weeks
end
Fetcher->>Parser: parse HTML -> day list
Parser-->>Fetcher: structured days/weeks
Fetcher->>Merger: merge years, dedupe, slice last 365 days, pad/sunday-align
Merger-->>Fetcher: merged grid
Fetcher-->>Handler: contributions grid
Handler-->>Client: JSON result
Estimated code review effort🎯 4 (Complex) | ⏱️ ~60 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
🧪 Generate unit tests (beta)
Comment |
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (35 files)
|
There was a problem hiding this comment.
Pull request overview
This PR releases version 1.3.0 of Snake Evolution, focusing on implementing a full rolling year contribution window, performance optimizations, and comprehensive documentation improvements. The release transitions the project to show a complete 12-month rolling contribution window ending on the current date, fixes animation speed defaults, and adds extensive package-level documentation.
Changes:
- Full rolling year implementation with proper Sunday alignment and merged data from current + previous year
- Default frame delay optimized from 150ms to 60ms for smoother animations
- Comprehensive README documentation added to all packages and directories
- Node.js requirements updated to >=24 with Bun 1.3.7
- Script consolidation in root package.json (30 → 21 scripts)
- Version bumps across all packages to 1.3.0
Reviewed changes
Copilot reviewed 50 out of 58 changed files in this pull request and generated 11 comments.
Show a summary per file
| File | Description |
|---|---|
packages/github/src/index.ts |
Core rolling year implementation with dual-year fetching, Sunday alignment, and UTC date parsing |
packages/cli/src/index.ts |
Frame delay default changed from 150ms to 60ms |
packages/cli/package.json |
Node requirement updated to >=24, @types/node downgraded to ^24.0.0 |
package.json |
Script consolidation, Bun 1.3.7 upgrade, dependency updates |
turbo.json |
Removed test caching and unused task configurations |
README.md |
Major restructuring with simplified quick start and copyright changes |
apps/web/src/content/docs/guides/gif-implementation.md |
New comprehensive GIF implementation guide (planned feature) |
apps/web/src/content/docs/roadmap.md |
New roadmap with 2026 dates and strategic positioning |
| Multiple package README files | New documentation for all packages and directories |
CHANGELOG.md |
Release notes with added/changed/fixed/removed sections |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6a7fdf1a22
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
Actionable comments posted: 7
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
__tests__/package-config.test.ts (2)
27-31: Pipeline failure: Node.js version regex mismatch 🚨The CI pipeline is failing because the test expectsengines.nodeto match/>=\s*22/but Node.js 24.x is now the Active LTS version (codename "Krypton"), and it appearspackage.jsonhas been updated to require>=24.The test regex needs to be updated to match the new Node.js requirement:
🔧 Fix to align test with updated Node.js requirement
test("should specify Node.js >= 22", () => { + test("should specify Node.js >= 24", () => { expect(pkg.engines).toBeDefined(); const engines = pkg.engines as Record<string, string>; - expect(engines.node).toMatch(/>=\s*22/); + expect(engines.node).toMatch(/>=\s*24/); });
195-200: Update test to require Node.js >= 24Both
package.jsonandpackages/cli/package.jsonspecify"node": ">=24", but this test is checking for>=22. The test name and regex pattern need to be updated to match the actual engine requirement.Suggested fix
- test("should require Node.js >= 22", () => { + test("should require Node.js >= 24", () => { expect(pkg.engines).toBeDefined(); const engines = pkg.engines as Record<string, string>; - expect(engines.node).toMatch(/>=\s*22/); + expect(engines.node).toMatch(/>=\s*24/); });
🤖 Fix all issues with AI agents
In @.vscode/snake-evolution.code-workspace:
- Around line 11-14: Remove the duplicated workspace folder entry that points to
"../apps/api": locate the two JSON objects with "path": "../apps/api" (the
entries whose "name" values are " |___⚡ API" and "⚡ apps/api") and delete
one of them so the apps/api folder appears only once in the workspace; keep
whichever "name" label you prefer and ensure the remaining entry still has
"path": "../apps/api".
In `@apps/web/src/content/docs/guides/gif-implementation.md`:
- Line 10: Update the status line "**Status: Planned for v1.3.0 (January
2026)**" to indicate the feature is released; replace it with a phrase such as
"**Status: Released in v1.3.0**" or "**Implemented in v1.3.0**" so the document
reflects this PR being the v1.3.0 release (locate the line containing the exact
status text and edit it accordingly).
In `@apps/web/src/content/docs/roadmap.md`:
- Around line 8-9: Update the roadmap entries so they aren’t “past-dated future”
items: locate the "**Updated:** January 2026" header and the timeline lines
referencing "Q1–Q3 2025" and "January 2025" and either (a) mark those items as
completed/retrospective with a short completion note and date, or (b) shift
their dates to current/future targets and adjust statuses to "In
Progress"/"Planned"; ensure similar edits are applied to all affected lines
(around lines 46–127) so the document’s dates/statuses are consistent and not
misleading.
- Around line 19-33: Update the Market Context and Our Opportunity sections to
add sourcing and timestamping: append "as of <month year>" to each star count
and the TARGET line, and add inline citations or link references for the GitHub
star numbers and any target rationale; specifically change the strings under the
"### Market Context" bullet points and the text block under "### Our
Opportunity" (including the gitfiti, github-activity, Snake Evolution lines and
"TARGET: 10K ⭐ in 6 months") to include either a parenthetical source URL or a
footnote-style citation and a last-updated date so readers can verify and know
when the metrics were recorded.
In `@apps/web/src/content/docs/testing/unit-tests-generated.md`:
- Around line 184-186: Replace the confusing placeholder line "cd <repo-root>"
in the command block with a clear instruction to run the command from the
repository root; specifically, update the doc lines that currently show "cd
<repo-root>" and "bun test" so the text reads something like "Run all tests from
the repository root" followed by the "bun test" command (leave "bun test"
unchanged) to avoid readers typing the literal placeholder.
In `@packages/biome-config/README.md`:
- Around line 9-13: Update the example JSON in README.md so the "$schema" value
matches the project's Biome version: replace
"https://biomejs.dev/schemas/2.0.6/schema.json" with
"https://biomejs.dev/schemas/2.3.13/schema.json" in the JSON snippet (the line
containing "$schema") to keep the documentation consistent with the biome.json
files.
In `@README.md`:
- Around line 62-68: Update the GitHub Actions step "Push to Output Branch" that
currently uses crazy-max/ghaction-github-pages@v3.1.0 to the latest major (use
`@v4` or pin to `@v4.2.0`); edit the action reference string in the workflow example
so the uses line reads crazy-max/ghaction-github-pages@v4 (or `@v4.2.0`) while
leaving the surrounding keys (target_branch, build_dir, env, GITHUB_TOKEN)
unchanged.
🧹 Nitpick comments (8)
packages/types/README.md (1)
32-34: Minor doc polish: hyphenate compound adjective.
“Full-year” reads better as a modifier.✏️ Suggested tweak
-| `ContributionGrid` | Full year contribution grid | +| `ContributionGrid` | Full-year contribution grid |.vscode/snake-evolution.code-workspace (1)
39-50: External paths may not exist for other contributors.The workspace includes paths that reference directories outside the repository (
../../snake-knowledge,../../contributions-devouring-snake,../../). These appear to be developer-specific folders that won't exist for other contributors cloning this repo.If this workspace file is meant to be shared, consider either:
- Removing these external references, or
- Adding a comment explaining these are optional/personal additions
If it's intentionally a personal setup, this is fine — just wanted to flag it in case it was unintentional! 🙂
packages/github/src/index.ts (3)
207-223: Good graceful degradation for new users.The error handling correctly swallows 404s for the previous year (new users won't have data) while propagating other errors like rate limits or network issues. This is a nice touch for robustness!
One small note: the string matching on
"User not found"or"404"(line 213) is somewhat fragile. If the error message format changes, this could break. Consider also checking for the error type or status code if available.
245-247: Deduplication works but could be more efficient.The
findIndexapproach is O(n²) for deduplication. For the typical ~730 days of data this is fine, but if you ever need to optimize, aSetorMapkeyed by date would be O(n).Not urgent, just a note for the future!
363-372: Sunday alignment logic is duplicated.This UTC-based Sunday alignment (lines 363-372) mirrors the logic in
fetchContributionsHTML(lines 280-286). Consider extracting to a shared helper function if you want to reduce duplication, though it's not critical.packages/renderer/README.md (2)
57-57: Clarify the version reference for Glass theme.The note states "GIF only, v1.1+" but this PR is releasing v1.3.0. Should this reference be updated to reflect the actual release version where Glass theme support was introduced?
39-45: Consider documenting GIF rendering APIs.The API table focuses exclusively on SVG rendering functions, but the package also exports
renderAnimatedGIFandrenderAnimatedGIFSampled(documented in the GIF implementation guide). While the README describes itself as "SVG renderer", users might benefit from a note pointing to the GIF guide or a brief mention that GIF rendering is also available.apps/web/src/content/docs/guides/gif-implementation.md (1)
144-146: Consider stricter validation for sampleRate.The current logic treats
sampleRate <= 1as "no sampling," which means a value of 0 or negative would be silently treated as 1. Consider adding validation to ensuresampleRateis a positive number.✨ Suggested validation improvement
export async function renderAnimatedGIFSampled( frames: SnakeFrame[], options: GifOptions & { sampleRate?: number } = {} ): Promise<Buffer> { const { sampleRate = 1, ...gifOptions } = options; + if (sampleRate < 1) { + throw new Error("sampleRate must be >= 1"); + } + if (sampleRate <= 1) { return renderAnimatedGIF(frames, gifOptions); }
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Fix all issues with AI agents
In `@__tests__/docs/documentation.test.ts`:
- Around line 16-21: The test currently allows any markdown heading level
because hasHeading uses /^#+\s*.*Snake Evolution/i; tighten this to match only
H1 or an explicit <h1> by changing the hasHeading pattern to require a single
leading '#' (e.g. /^#\s*Snake Evolution/i) and add an HTML <h1> check (e.g.
/<h1.*>.*Snake Evolution.*<\/h1>/i) so the test function ("should have main
heading or banner") only passes for a true main heading or the existing banner
check; update the hasHeading/hasBanner logic in the test accordingly
(referencing hasHeading, hasBanner, readmePath, content).
In `@package.json`:
- Around line 25-27: The root package.json scripts create an infinite loop
because "typecheck" runs "turbo run type-check" which in turn runs the root's
"type-check" (which calls "bun run typecheck"); fix by changing the "typecheck"
script to invoke Turbo only for workspace packages and explicitly exclude the
root (use Turbo's --filter or negated filter syntax to omit the root package) so
"typecheck" no longer triggers the root "type-check"; update the "typecheck"
script entry to use a Turbo filter excluding the root while leaving "type-check"
and "check" unchanged.
🧹 Nitpick comments (4)
__tests__/docs/documentation.test.ts (1)
211-217: Remove duplicate doc entries to avoid redundant checks
Both lists include../../.github/CONTRIBUTING.mdtwice, which adds unnecessary work and noise in failures.Suggested cleanup
const docs = [ "../../README.md", - "../../.github/CONTRIBUTING.md", - "../../.github/CONTRIBUTING.md", + "../../.github/CONTRIBUTING.md", "../../RELEASE_SETUP.md", "../../apps/web/src/content/docs/roadmap.md", ]; @@ const docs = [ { path: "../../README.md", minSize: 2000 }, - { path: "../../.github/CONTRIBUTING.md", minSize: 3000 }, - { path: "../../.github/CONTRIBUTING.md", minSize: 3000 }, + { path: "../../.github/CONTRIBUTING.md", minSize: 3000 }, { path: "../../RELEASE_SETUP.md", minSize: 500 }, { path: "../../apps/web/src/content/docs/roadmap.md", minSize: 1000 }, ];Also applies to: 232-238
packages/github/src/index.ts (2)
245-247: Consider using a Map for deduplication.The current
findIndexapproach is O(n²). With ~730 days max it won't be a problem in practice, but aMapwould be cleaner and O(n):✨ Optional refactor using Map
- // 3. Remove duplicates (overlap at year boundary?) - const uniqueDays = allDays.filter( - (day, index, self) => index === self.findIndex((d) => d.date === day.date), - ); + // 3. Remove duplicates (overlap at year boundary?) + const dayMap = new Map<string, GitHubContribution>(); + for (const day of allDays) { + if (!dayMap.has(day.date)) { + dayMap.set(day.date, day); + } + } + const uniqueDays = Array.from(dayMap.values());
331-357: Regex patterns have a minor attribute-order blind spot.Both patterns assume
data-countappears betweendata-dateanddata-level. If GitHub serves HTML like:<td data-date="2025-01-01" data-level="3" data-count="4">...the count won't be captured. Not a blocker since the
contributionCountFromLevelheuristic kicks in, and the comment on lines 316-317 acknowledges this. Just something to keep in mind if you ever see unexpectedly heuristic-based totals.💡 Alternative: capture attributes separately
If you wanted bulletproof extraction, you could capture the whole
<td>tag and then run separate regex matches for each attribute:const tdPattern = /<td([^>]*)>/g; for (const match of html.matchAll(tdPattern)) { const attrs = match[1]; const dateMatch = attrs.match(/data-date="(\d{4}-\d{2}-\d{2})"/); const levelMatch = attrs.match(/data-level="(-?\d+)"/); const countMatch = attrs.match(/data-count="(\d+)"/); if (dateMatch && levelMatch) { days.push({ date: dateMatch[1], level: Number.parseInt(levelMatch[1], 10), count: countMatch ? Number.parseInt(countMatch[1], 10) : undefined, }); } }This handles any attribute order. But again, totally optional—current approach works fine!
README.md (1)
83-103: Consider clarifying the asset path for generated outputs.
The examples reference./assets/examples/..., which is perfect for this repo, but users running the Action will typically have outputs underdist/on the output branch. A short note would reduce confusion.📝 Suggested clarification
### Markdown Usage Add this into your README.md +_(If using the GitHub Action, reference the generated files from the output branch, e.g., `dist/snake.svg`.)_ ```markdown </details> </blockquote></details> </blockquote></details> <!-- This is an auto-generated comment by CodeRabbit for review status -->
… up VS Code workspace configuration.
…or handling, update roadmap dates to 2026, and bump Node.js engine requirement to v24.
There was a problem hiding this comment.
Actionable comments posted: 5
🤖 Fix all issues with AI agents
In `@apps/web/src/content/docs/roadmap.md`:
- Around line 19-33: Update the market statistics in the "Market Context" and
"Our Opportunity" sections by appending a timestamp (e.g., "as of Jan 2026") to
each metric and adding verifiable sources: convert lines like "18,000+ GitHub
stars", "5,500+ stars" and the inline block containing "TARGET: 10K ⭐" to
include either a repository link or a GitHub search query reference in
parentheses or square brackets (e.g., "(as of Jan 2026, see [repo-name] or
[GitHub search])"), and change the target timeline text "TARGET: 10K ⭐ in 6
months" to a concrete date like "TARGET: 10K ⭐ by July 2026" so readers can
verify numbers and timeline.
- Line 30: Update the "github-activity" line to remove the all-caps "SKETCHY"
label and replace it with a more measured descriptor (for example "manipulation
tool" or "potentially inauthentic approach"); locate the entry containing the
string "github-activity: Fake automation, 3.7K ⭐, SKETCHY" and edit the
trailing label to a professional phrasing that preserves the intended warning
without using pejorative all-caps language.
In `@package.json`:
- Line 48: The engines entry currently pins Node to "node": ">=24" but the
codebase doesn't use Node 24-specific features; update the engines field in
package.json (the "node" engines entry) to a lower minimum such as ">=22" (or
">=20" if you verified compatibility), and update any CI configs or
README/tooling that enforce Node 24 to match the new floor to make the project
more inclusive for contributors and CI environments.
In `@packages/github/src/index.ts`:
- Around line 252-258: The date filtering uses toISOString() on local Date
objects (fromDate/toDate) which converts to UTC and can mismatch the local
YYYY-MM-DD values in uniqueDays; fix by generating date strings in UTC
explicitly (use getUTCFullYear/getUTCMonth/getUTCDate) or a small helper to
format dates as YYYY-MM-DD in UTC for fromDate and toDate, and ensure the same
UTC-based strings are used when computing oneYearAgo and when filtering
rollingDays against uniqueDays (refer to oneYearAgo, fromDate, toDate,
rollingDays, uniqueDays).
In `@turbo.json`:
- Around line 24-27: The turbo.json "format" task currently has "cache": true
which prevents the biome format --write . command (the "format" task) from
running on cache hits; change the "format" task's cache property to false
(matching "lint:fix") so the in-place formatter always runs when invoked,
updating the "format" task's "cache" value from true to false.
🧹 Nitpick comments (1)
packages/github/src/index.ts (1)
244-247: Minor: O(n²) deduplication could be simplified.The current
findIndex-based deduplication is O(n²). While the dataset is small (~730 days max), aMaporSetwould be more idiomatic and marginally faster:♻️ Optional refactor using Map
- const uniqueDays = allDays.filter( - (day, index, self) => index === self.findIndex((d) => d.date === day.date), - ); + const dayMap = new Map<string, GitHubContribution>(); + for (const day of allDays) { + if (!dayMap.has(day.date)) { + dayMap.set(day.date, day); + } + } + const uniqueDays = Array.from(dayMap.values());
…d refine documentation examples and formatting.
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@packages/renderer/README.md`:
- Around line 25-33: The README's static render example contains a
duplicated/malformed block: remove the stray incomplete declaration and keep a
single correct call to renderStaticSVG assigning to staticSvg; locate the
duplicated lines around the staticSvg = renderStaticSVG(...) example and ensure
the final code is a single well-formed statement using renderStaticSVG(grid,
snake, { cellSize: 12, gap: 2, palette: 'github-light' }) so only one staticSvg
variable is declared and the object literal is closed properly.
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 52 out of 59 changed files in this pull request and generated 4 comments.
Comments suppressed due to low confidence (1)
.vscode/snake-evolution.code-workspace:38
- The apps/api folder is defined twice in the workspace configuration. It appears once with the new naming scheme at line 12 (" |___⚡ API") and again with the old naming scheme at lines 35-38 ("⚡ apps/api"). This duplication should be removed to avoid confusion in VS Code.
{
"name": "⚡ apps/api",
"path": "../apps/api"
}
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: Miccy <code@miccy.dev>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: Miccy <code@miccy.dev>
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@CHANGELOG.md`:
- Around line 32-33: The CI failure is caused by malformed Markdown headings in
CHANGELOG.md; add a blank line above and below each section heading (e.g., "###
Changed" and "### Fixed") and either add content under "### Changed" or remove
the empty "### Changed" heading entirely so no empty section remains; ensure the
resulting file has a blank line separation between headings and their content
(or between consecutive headings) to satisfy the linter.
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> Signed-off-by: Miccy <code@miccy.dev>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> Signed-off-by: Miccy <code@miccy.dev>
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@packages/github/src/index.ts`:
- Around line 96-115: The rolling-year branch in packages/github/src/index.ts
computes `from`/`to` using full ISO timestamps that preserve time-of-day
(variables: now, oneYearAgo, from, to), causing inconsistency with calendar-year
mode and the HTML scraping path; modify the rolling-year logic to align the
start to the previous Sunday as you already do but then normalize both `from`
and `to` toUTC date boundaries (set `from` to YYYY-MM-DDT00:00:00Z and `to` to
YYYY-MM-DDT23:59:59Z) so GraphQL and calendar modes use consistent, clean UTC
day-range strings.
🧹 Nitpick comments (1)
packages/github/src/index.ts (1)
205-223: Prefer status-aware errors over string matching for 404 handling.String checks on
error.messagecan misclassify failures. Attachingstatusto the error makes the fallback more robust and easier to reason about.🔧 Example refactor (status-carrying error)
- if (!response.ok) { - if (response.status === 404) throw new Error(`User not found: ${username}`); - throw new Error(`GitHub error: ${response.status}`); - } + if (!response.ok) { + const err = new Error( + response.status === 404 ? `User not found: ${username}` : `GitHub error: ${response.status}`, + ) as Error & { status?: number }; + err.status = response.status; + throw err; + }- fetchYear(username, currentYear - 1).catch((error) => { + fetchYear(username, currentYear - 1).catch((error) => { + const status = (error as { status?: number }).status; // Only swallow 404s (User not found) or "Not Found" errors // Propagate other errors (rate limits, network issues, etc.) - const msg = error instanceof Error ? error.message : String(error); - if (msg.includes("User not found") || msg.includes("404")) { + if (status === 404) { return { weeks: [], totalContributions: 0, year: currentYear - 1, username, } as ContributionGrid; } throw error; }),
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
packages/renderer/src/renderer.test.ts (1)
609-616: Test assertions at lines 609-616 won't match the rendered SVG output due to tapering offsets.The test expects exact string matches like
x="3" y="3", but the implementation applies tapering offsets:
- Head (i=0):
sizeMultiplier = 1.3→segSize = 14→offset = -1.5→ actual x becomes3 + (-1.5) = 1.5- Second segment (i=1):
sizeMultiplier = 0.7→segSize = 8→offset = 1.5→ actual x becomes17 + 1.5 = 18.5These position assertions will fail. Update the test to either expect the offset-adjusted positions or change the assertion strategy (e.g., check for segment presence without relying on exact pixel values).
🤖 Fix all issues with AI agents
In `@packages/renderer/src/index.ts`:
- Line 92: Fix the minor comment typo in packages/renderer/src/index.ts by
changing the comment text in the tapering logic comment (near the
renderAnimatedSVG-related code) from "Tapering logic matchin renderAnimatedSVG"
to "Tapering logic matching renderAnimatedSVG" so the comment correctly reads
"matching".
🧹 Nitpick comments (1)
README.md (1)
133-145: Consider simplifying the wording.The phrase "prefer to have" on line 135 is a bit wordy. A more direct phrasing would read better.
✏️ Suggested simplification
-If you prefer to have the tool available globally: +To install the tool globally:
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> Signed-off-by: Miccy <code@miccy.dev>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> Signed-off-by: Miccy <code@miccy.dev>
Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com> Signed-off-by: Miccy <code@miccy.dev>
Release v1.3.0
🚀 Major Improvements
data-countwhen available and robustly approximate fromdata-levelotherwise.docs/guides/gif-implementation.mdas a planned feature for v1.3.0 (Jan 2026).🐛 Bug Fixes
📝 Documentation
roadmap.mdto reflect 2025 timeline.packages/renderer/README.md.✅ Verification
qualityscript to rootpackage.json.Summary by CodeRabbit
New Features
Documentation
Changes
Chores
✏️ Tip: You can customize this high-level summary in your review settings.